This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
So I'm trying to remember what exactly may have been the reason why my own experience with Delete was so negative. The only thing I can remember is that some of my custom classes had a Sub Delete, and if memory (mine ;-) serves well, I was able to avoid the crashes (occurring after calling explicit Delete) when I outcommented all my Sub Deletes.
I never got to know exactly why Delete was crashing my code, because in the meanwhile I had re-organized it, so out-of-memory problems were gone. Key was three things, in descending order of relevance: (a) avoid keeping many -- more than a few dozens -- NotesDocument instances in memory at the same time, (b) re-use objects whenever possible, instead of re-instantiating them, and (c) eliminate cyclic object references.
Anyway, I'll certainly give Delete a closer look, next time I'll have an opportunity (a need, that is) to.
P.S.
I just looked up my related thread in the Partner Forum 2004 (oh my, that long ago...) Julie Kadashevich responded <quote>"By doing a delete the object chain is put in a bad state. So, when the official clean up happens at agent termination LotusScript gets into an infinite loop."</quote> I think her response was what ultimately made me stay away from using explicit Delete.
Feedback response number WEBB88UMLG created by ~Chris Frofootherobu on 08/31/2010
interesting
Return to top
. . . . . . interesting (~Tip Zekjumitex... 31.Aug.10) 
